Remember referenced repositories as system repositories instead of user #512
Conversation
laeubi
changed the title
|
I see that org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.checkForUpdates(String, IQuery) calls org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.getAvailableRepositories() which calls org.eclipse.equinox.p2.repository.IRepositoryManager.getKnownRepositories(int) with argument org.eclipse.equinox.p2.repository.IRepositoryManager.REPOSITORIES_ALL. As such, is accurate to conclude that not showing the repositories to the user actually has no impact on how Check for Updates will behave after the repo is added (discovered), regardless of whether the repo is marked system or not? If so, this change does not actually address the "Even worse..." aspect described in the first comment. If not, what am I overlooking? It's rather disconcerting that there are repositories that will be contacted and used but you can't see , remove, nor disable them.... |
|
I can't tell much about If one wants to see "everything" I'm sure the UI can be enhanced to support that use-case but this really focus on the part that I don't get new user repositories as a side effect of performing a check for updates. |
|
A possible UI might look like this (or as part of the filter bar):
but as said that's nothing I'd like to address with this PR. |
|
If you checked in the debugger then I’m reassured and this looks like a nice change. I had the same idea about a check box to show system repositories; it would help debug. |
|
If such thing is required I think it should (again) be an UI thing so when I add the site I can select to also add references and maybe select what I want to have added. |
|
It’s not required. It’s just a thought. |
laeubi
force-pushed
the
rember_as_system
branch
3 times, most recently
from
77e4fb3
to
3199f3f
Compare
Currently there is a quite surprising behavior, that if a user adds an updatesite that contains a referenced repository, that after an update-check additional repositories are visible. Even worse these are now used additionally to check for updates and if they contain other references these are also added and so on. This can result not only in a long list of sites the user never has added and has no clue where they are coming from but even pulling in unwanted or conflicting updates. This now distinguishes two cases: 1) A repository is discovered by the RepositoryAction it is handled as a user added repository and becomes visible 2) A repository is discovered by a reference in that case it is handled as a system repository and not becomes visible that way the list of user visible repositories stay clean from referenced repositories and unexpected side effects on update checks.
I now added |
|
Kudos for investing your time on these improvements! 🏅 |
|
No problem, this was an issue for too long now and seem to regularly cause confusions. |
Currently there is a quite surprising behavior, that if a user adds an
updatesite that contains a referenced repository, that after an
update-check additional repositories are visible. Even worse these are
now used additionally to check for updates and if they contain other
references these are also added and so on. This can result not only in a
long list of sites the user never has added and has no clue where they
are coming from but even pulling in unwanted or conflicting updates.
Before this change
Here is an example with the m2e update site (
https://download.eclipse.org/technology/m2e/snapshots/latest/):In the first step there is only this single site:
Now I go to
Help > Check For Updatesand after this completes I end up with the following list (10 sites):Now I repeat and perform
Help > Check For Updatesand after this completes I end up with the following list (12 sites):After this changes
This now distinguishes two cases:
user added repository and becomes visible
as a system repository and not becomes visible
that way the list of user visible repositories stay clean from
referenced repositories and unexpected side effects on update checks.
FYI @merks @HannesWell @jonahgraham